|
OpenStack Queens : Use Cinder Storage (LVM)
2018/03/15 |
|
It's possible to use Virtual Storages provided by Cinder if an Instance needs more disks.
Configure Virtual storage with LVM backend on here.
It needs there are some free spaces on disks of Storage Node.
------------+---------------------------+---------------------------+------------
| | |
eth0|10.0.0.30 eth0|10.0.0.50 eth0|10.0.0.51
+-----------+-----------+ +-----------+-----------+ +-----------+-----------+
| [ Control Node ] | | [ Network Node ] | | [ Compute Node ] |
| | | | | |
| MariaDB RabbitMQ | | L2 Agent | | Libvirt |
| Memcached httpd | | L3 Agent | | Nova Compute |
| Keystone Glance | | Metadata Agent | | L2 Agent |
| Nova API | | Cinder-Volume | | |
| Neutron Server | | | | |
| Metadata Agent | | | | |
| Cinder API | | | | |
+-----------------------+ +-----------------------+ +-----------------------+
|
| [1] | Create a volume group for Cinder on Storage Node. |
|
root@storage:~# pvcreate /dev/sdb1 Physical volume "/dev/sdb1" successfully created root@storage:~# vgcreate -s 32M vg_volume01 /dev/sdb1 Volume group "vg_volume01" successfully created |
| [2] | Configure Cinder Volume on Storage Node. |
|
root@storage:~#
apt-get -y install tgt thin-provisioning-tools
root@storage:~#
vi /etc/cinder/cinder.conf # add a value for enabled_backends enabled_backends = lvm
# add follows to the end [lvm] iscsi_helper = tgtadm # volume group name just created volume_group = vg_volume01 # IP address of Storage Node iscsi_ip_address = 10.0.0.50 volume_driver = cinder.volume.drivers.lvm.LVMVolumeDriver volumes_dir = $state_path/volumes iscsi_protocol = iscsi systemctl restart cinder-volume tgt
|
| [3] | Configure Nova on Compute Node. |
|
root@node01:~#
vi /etc/nova/nova.conf # add to the end [cinder] os_region_name = RegionOne systemctl restart nova-compute
|
| [4] | Login as a common user you'd like to add volumes to own instances. For example, create a virtual disk [disk01] with 10GB. It's OK to work on any node. (This example is on Control Node) |
|
# set environment variable first ubuntu@dlp ~(keystone)$ echo "export OS_VOLUME_API_VERSION=2" >> ~/keystonerc ubuntu@dlp ~(keystone)$ source ~/keystonerc
openstack volume create --size 10 disk01 +---------------------+--------------------------------------+ | Field | Value | +---------------------+--------------------------------------+ | attachments | [] | | availability_zone | nova | | bootable | false | | consistencygroup_id | None | | created_at | 2018-03-15T10:21:07.000000 | | description | None | | encrypted | False | | id | e28a1b77-fb0f-4bc0-96dc-283a113be0e4 | | multiattach | False | | name | disk01 | | properties | | | replication_status | None | | size | 10 | | snapshot_id | None | | source_volid | None | | status | creating | | type | None | | updated_at | None | | user_id | b7b1b4b96b714e458690dd893fbbe5f5 | +---------------------+--------------------------------------+ubuntu@dlp ~(keystone)$ openstack volume list +--------------------------------------+--------+-----------+------+-------------+ | ID | Name | Status | Size | Attached to | +--------------------------------------+--------+-----------+------+-------------+ | e28a1b77-fb0f-4bc0-96dc-283a113be0e4 | disk01 | available | 10 | | +--------------------------------------+--------+-----------+------+-------------+ |
| [5] | Attach the virtual disk to an Instance. For the exmaple below, the disk is connected as [/dev/vdb]. It's possible to use it as a storage to create a file system on it. |
|
ubuntu@dlp ~(keystone)$ openstack server list +-----------+-------------+---------+-----------------------------------+------------+----------+ | ID | Name | Status | Networks | Image | Flavor | +-----------+-------------+---------+-----------------------------------+------------+----------+ | fffbf3f6- | Ubuntu_1604 | SHUTOFF | int_net=192.168.100.8, 10.0.0.208 | Ubuntu1604 | m1.small | +-----------+-------------+---------+-----------------------------------+------------+----------+
ubuntu@dlp ~(keystone)$
openstack server add volume Ubuntu_1604 disk01
# the status of attached disk turns [in-use] like follows ubuntu@dlp ~(keystone)$ openstack volume list +--------------------------------------+--------+--------+------+--------------------------------------+ | ID | Name | Status | Size | Attached to | +--------------------------------------+--------+--------+------+--------------------------------------+ | e28a1b77-fb0f-4bc0-96dc-283a113be0e4 | disk01 | in-use | 10 | Attached to Ubuntu_1604 on /dev/vdb | +--------------------------------------+--------+--------+------+--------------------------------------+ # for detaching the disk, run like follows ubuntu@dlp ~(keystone)$ openstack server remove volume Ubuntu_1604 disk01 |